-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow multiple summaries per pull request #53
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI, this is a first working draft and still rough around the edges / missing documentation. But see the comments for some early discussion & context.
The new dataclass ChangeNote helps with uncoupling the `_query.py` logic and the `_format.py` logic from each other somewhat. In this case one pull request can be turned into multiple change notes which might appear in separate sections. This optional behavior allows to deal with somewhat large or unfocused pull requests. Long-term this step would also be necessary in case PyGitHub is replaced with a GraphQl-based approach.
The new dataclass Contributor helps with uncoupling the `_query.py` logic and the `_format.py` logic from each other somewhat. Long-term this step would also be necessary in case PyGitHub is replaced with a GraphQl-based approach.
Querying and formatting might generate warnings. Make sure that these are printed before the generated notes.
a89f0ed
to
72e88ce
Compare
This is nothing to fancy but it should catch unexpected changes in our formatting logic and cover the happy path.
9e88b20
to
bc5fef4
Compare
bc5fef4
to
62cbdac
Compare
Okay, finally Python 3.9 is happy (sorry for the notification noise). I think this is ready to merge. As a real world example, this
includes just the merge commit from scikit-image/scikit-image#6695 and creates the following notes: Details# scikit-image x.y.z
We're happy to announce the release of scikit-image x.y.z!
## New Features
- Add parameter `mode` to `binary_erosion`, `binary_dilation`, `binary_opening` and `binary_closing` in`skimage.morphology`. These new parameters determine how array borders are handled ([#6695](https://github.com/scikit-image/scikit-image/pull/6695)).
- Add parameters `mode` and `cval` to `erosion`, `dilation`, `opening`, `closing`, `white_tophat`, and `black_tophat` in `skimage.morphology`. These new parameters determine how array borders are handled ([#6695](https://github.com/scikit-image/scikit-image/pull/6695)).
- Add functions `mirror_footprint` and `pad_footprint` to `skimage.morphology` ([#6695](https://github.com/scikit-image/scikit-image/pull/6695)).
## API Changes
- Parameters `shift_x` and `shift_y` in `skimage.morphology.erosion` and `skimage.morphology.dilation` are deprecated. Use `pad_footprint` or modify the footprint manually instead ([#6695](https://github.com/scikit-image/scikit-image/pull/6695)).
## Bug Fixes
- Ensure `skimage.morphology.closing` and `skimage.morphology.opening` are extensive and anti-extensive, respectively, if the footprint is not mirror symmetric ([#6695](https://github.com/scikit-image/scikit-image/pull/6695)).
## Contributors
2 authors added to this release (alphabetically):
- Cris Luengo ([@crisluengo](https://github.com/crisluengo))
- Lars Grüter ([@lagru](https://github.com/lagru))
3 reviewers added to this release (alphabetically):
- Cris Luengo ([@crisluengo](https://github.com/crisluengo))
- Lars Grüter ([@lagru](https://github.com/lagru))
- Stefan van der Walt ([@stefanv](https://github.com/stefanv))
_These lists are automatically generated, and may not be complete or may contain
duplicates._ Let me know what you think. :) |
@stefanv, could I ask you to have a look at this if you have the time? 🙏 Not the highest priority in my opinion but I'd hate to rush this just before our next skimage release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @lagru, this looks good overall. I suggested a syntax change to how the label is indicated.
Co-authored-by: Stefan van der Walt <[email protected]>
Co-authored-by: Stefan van der Walt <[email protected]>
@lagru Let me know if you intend to make any other changes, otherwise I'll merge. |
This syntax should hopefully be more robust than the previous one based on the relatively common ":" character.
@stefanv. I've addressed all your comments and switched to the I've also added basic tests for this in |
Attempts to make the usage of the new feature clearer.
As we talked about, I've added a section in the README to document the new feature and make it clearer how to use it. It's duplicating the documentation in the config a little bit, but it's probably less hidden this way and should read nicer (no talk of regex). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great! Is overriding the title documented?
By default, changelist will fall back to the title of a pull request and its | ||
GitHub labels to sort it into the appropriate section. However, if you want | ||
longer summaries of your changes you can add a code block with the following | ||
form anywhere in the description of the pull request: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stefanv, re #53 (review): yes, overriding the title is documented.
Co-authored-by: Stefan van der Walt <[email protected]>
Thanks Lars! |
Tackles the first case in #45:
It would be good to have this in before the next release of scikit-image. So that changelist can gracefully deal with scikit-image/scikit-image#6695.